Did any of the Microsoft-bashers here even read the article? Microsoft responds in the comments and says the issue is already fixed in internal builds and will ship with Silverlight 5 RTM.