No, I downloaded the 4.0.5 source, compiled with JDK 5.0, and used the EJB3 build of the server.
The root exception "ClassNotFoundException: No ClassLoaders found for: org.jboss.jms.destination.JBossQueue" can be generated by many other things, including a "legitimate" missing class. I agree it's not the case here, but adding a message directing the user to specifically look for a extraneous "jndi.properties" can be misleading. That's why I would rather list this under FAQs, as a possible cause.
What's a little bit more worrisome is the fact that the root exception shows nowhere in the logs.
I can see it is linked to a new JMSException
{ JMSException x = new JMSException("Error creating the dlq connection: " + e.getMessage()); x.setLinkedException(e); throw x; }
I added a Wiki entry for this under Miscellanea. http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossJMSEJB3MDB
I also posted a patch patch request in the EJB developer's forum (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974364)
Thanks.