Many people have built their own logging frameworks for prior versions of SSIS and I anticipate that many will want to integrate those solutions with the new SSIS Catalog in SSIS 2012.
Typically this will be done by creating new tables and stored procedures in the [SSISDB] database however this presents a problem. The package execution process knows which server the [SSISDB] database resides on (thus enabling it to log to it) but the packages themselves do not.
Similarly package developers may wish to interrogate [SSISDB] to discover things about their in-flight executions (e.g. When did the execution begin?)
Typically then developers are going to have to pass in the name of the server hosting [SSISDB] when a package is executed. This is possible using @@SREVERNAME but its its still a bit unwieldy - it would be better if the location of [SSISDB] were available to every package that gets executed against that catalog.
I understand that you'll need to wait until SSIS2012 hits the streets and you get real feedback from customers before deciding whether a solution here is necessary or not - so this Connect submission is really just to make you aware that this situation is going to crop up (please don't use that as an excuse to close this Connect submission though).