We migrate our production server from 2.4.4 to 3.2.3. When I deploy our "old" apps (mostly based on BMPs at this time), I get what seems to be a hot-deployment problem on one specific bean, only on one application. I had to modify the bean's content (reading the logs told me there was an issue at line 214, in the ejbLoad method). When I wanted to deploy a "fixed" version, the logs still read error on this same line (214), therefore this line is now number 218. This behaviour lets me thing the old bean is still running, instead of the new one.