I just tried duplicating the steps you mentioned and am getting the same behavior. This appears to be a bug. I would try to talk to someone in Premier Support or on the Product Team about it, to report it.