Redeploy of WAR files : EJBs become "null" in JNDI

SourceForge Submitter: roullian .
OS : Win2K
JDK : Sun 1.4.2 with -server

I have a war file (war A), and an ear file (ear A)
which contains a bunch of EJBs.
I have a second ear file (ear B) which contains another
war file (war B). (In this second case war B is
included in ear B, I also tested with war B outside of
ear B, but I still had the same exact problems).
war A is just accessing ear A, and has done so
successfully for several months.
war B is accessing EJBs included in ear A and ear B.
Hot redeploy of war A is ok.
But hot redeploy of ear B (which contains war B) causes
every code accessing ear A to fail (including war A).
This only occur when hot redeploying ear B (a clean
start works, for example). And if I'm using some EJB
from ear A during the hot redeploy of ear B, this EJB
will still work afterwards (however the other EJBs from
EAR A will stop working...).
This is clearly a very strange behavior, and I need
to have several apps deployed in JBoss...

Here is the way I access EJBs :
XDoclet-generated "util" file, with the "physical" (ie
JNDI) access. I'm currently testing with the "logical"
(ie java:comp/env) access.

Here is a typical error :
A ClassCastException, when doing the JNDI lookup. In
fact, it seems that JNDI is returning null, which
causes the the ClassCastException. No NamingException
returned. And the EJB is still visible in the JNDI
tree, but was not accessed (according to the stats in
the JBoss web console).

I can send you the various WARs/EARs if it can help, of
course.