From the perspective of JBoss EJB3.x changes, there have been many
user reported and other EJB3.x bug fixes that have been included JBoss
AS 6.0.0.M5. Other than the bug fixes, there has been one important
change to the way we deploy (our internal) JBoss EJB3.x timerservice.
This change involves deploying (our internal) timerservice
implementation "lazily". The timerservice is deployed only when the
server has any EJB3.x deployments. The change was done to improve the
JBoss AS boot time. We have explained the complete details of this
change in the wiki here http://community.jboss.org/wiki/LazyEJB31timerservicedeploymentstartingJBossAS600M5.