The bigger question is why wasn't this considered DURING the iOS5 beta? If it got brought to Apple's attention during the beta cycles and they decided to not fix it then they'll most likely won't fix it now either (although it seems like they really don't have much choice here but to provide a solution one way or another)
Fair point, but attention-grabbing blog posts are not the only way to get your voice heard as a developer. There's a difference between 'feedback' and 'creating public pressure'.
But I hear ya...
I wonder if there is any chance that Apple will change how this works - it seems like this should be doomsday for a large swath of apps.
(married to Smokey and partner on all these apps!)