The SQL Server Setup team has verified that this is a bug.  We are currently investigating, but at this point we do not have a workaround.

Further updates will be provided via this weblog as they become available.

-Jeffrey Baker
SQL Server Setup Development