I was running into this on SQL 2005 SP2 and found the following, which states that Microsoft is not intending on fixing this issue:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=361954