Oh, two more things: This call is going between a war and an ejb-jar, both in the same ear, so it might be due to misconfiguration somewhere. And if you're sure an upgrade would fix this, it would be gret to know, even though we are not able to do this. According to JBCL-185, though, as far as I can tell that fix isn't in any released version yet.