We have the same problem here. I have been digging into this problem, but have not found a solution yet. We have message-driven beans in our project, and if I remove the MDBs, the exception disappears. So I assume that the information in jndi.properties, which includes a value for parameter java.naming.factory.initial, is not available when undeploying an MDB. Hence, it could be a bug in JBoss. I will keep on elaborating on this issue and keep you informed if I find out something meaningful. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161074#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...