Using the code from the 3.4.0 CR1 release it appears that this behaviour has been fixed.
Reply to this message by going to Community
Start a new discussion in JBoss Web Services at Community