I just reproduced this with a testcase. So it does appear to be a bug. I'll look into this and create a JIRA. Thanks for bringing this up.
Reply to this message by going to Community
Start a new discussion in EJB 3.0 at Community