About time! Apple sneaked this fix thru very quietly, didn't they? Their policy seems to be 1. Don't admit a bug exists, 2. Fix it slowely, and 3. Once they've fixed it, pretend it never existed in the first place.
I didn't bother to check the update, because I didn't see any mention of the issue being fixed in the 5.2 update notes.
Thanks for letting us know.