I'm unable to reproduce this using a clean install of the latest code in svn, so either the bug has been fixed or it is somehow specific to upgraded installations. Todd, please let us know if the problem still occurs after you upgrade to the forthcoming release.
--Dean