Thanks to Greg and Kevin for this info, but honestly this is a little scary because it definately sounds like some people (internally) are arguing for it to "not" be in CS6, but to require users to pay for an upgrade to get this fix. This is totally unacceptable. Please let them know that this would be an almost certain nail in the coffin for my future plans with Adobe.
If they fix it in CS6 then some confidence will have been restored in Adobe and many of us may well upgrade to CS7 (or what ever comes next) "once the initial release quality becomes known". However, if they "don't" fix it in CS6 then frankly confidence in Adobe will be shattered and I will not be giving Adobe any money for any upgrades.
I know I'm not alone in this.... so future business from me and a few others at least rests upon Adobe doing the right thing for CS6 users.