Maintenance Plans fail on Named Instances?

I think this is a bug in SQL 2005 Maintenance Plans (the graphical designer part under Management\Maintenance Plans that creates an SSIS package), but I want to see if anyone knows for sure or can replicate it. Some items fail on named instances.

Example:
Whenever you create aCheck Database Integrety Taskfor databaseHappyTeston server instanceSQLMACHINE\SQL2005it fails every time with a message sayingALTER FAILED ON SERVER SQLMACHINE\\SQL2005. On top of that, it causes an Exception for the email sending last step of the task with something likeAn exception has occured, failed sending email, there was an error near SQLMACHINE.

Now, it's obvious what the problem is. SQLMACHINE\\SQL2005 doesn't exist and the email procedure params aren't escaped properly before sending them in (security issue here? I didn't try any injections). The quick solution has been just make a TSQL item and copy/paste the correct SQL into it for the server (you can actually even copy directly from the Check DB Integrety Task properties), which runs fine.

Can anyone else confirm this problem?