Marking an SFSB as clustered solely via <clustered>true</clue> is leading to NPE:

13:24:09,405 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:ear=bank.jar,jar=bank.jar,name=Bank,service=EJB3 state=Create
java.lang.AssertionError: ClusterConfigMetaData not found in metadata
at org.jboss.ejb3.proxy.clustered.jndiregistrar.JndiClusteredSessionRegistrarBase.getProxyFactoryRegistryKey(JndiClusteredSessionRegistrarBase.java:197)
at org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase.createJndiReferenceBindingSet(JndiSessionRegistrarBase.java:233)
at org.jboss.ejb3.proxy.clustered.jndiregistrar.JndiClusteredSessionRegistrarBase.createJndiReferenceBindingSet(JndiClusteredSessionRegistrarBase.java:212)
at org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase.bindEjb(JndiSessionRegistrarBase.java:162)
at org.jboss.ejb3.session.SessionSpecContainer.lockedStart(SessionSpecContainer.java:702)
at org.jboss.ejb3.stateful.StatefulContainer.lockedStart(StatefulContainer.java:294)
at org.jboss.ejb3.EJBContainer.start(EJBContainer.java:858)

Problem is no cluster-config element is specified in jboss.xml to drive the creation of a ClusterConfigMetaData, and the mechanism that drives creation of one from @Clustered contents doesn't kick in because there is no annotation.