It seems the problem explained in this post and this post has been solved in the Flex SDK 3.2 release.

A good thing then 🙂

Share and Enjoy!