Did you find a workaround? I'm experiencing exactly the same problem. It doesn't look like someone will fix it. :(
Reply to this message by going to Community
Start a new discussion in EJB3 at Community