JBoss 5.0 does not create missing* JMS destinations automatically as JBoss 4.2 does. In any case JBoss 4.2 issues a warning which may be uncomfortable for users. Hence a default jBPM destinations descriptor must be provided and offered as an option in the installer.

that is, referenced in jboss.xml or jboss-web.xml but not bound to JNDI