Hi Macro,
I did not reproduce this issue in the lastest jbossws native code base(3.4.0-SNAPSHOT). It seems this issue have been fixed after we move to Netty as client side http connection . Can you try the lastest jbossws-native-3.4.0-SNAPSHOT with jboss-6.0.0.M5 or jboss-6.0.0-SNAPSHOT to see if it works for your testcase ?
Thanks,
Jim