Looking at the the txtimer errors, these are due to previous deployments not getting cleaned up due to OOMEs:

2006-03-20 13:20:21,455 WARN [org.jboss.system.ServiceController] Problem start
ing service jboss.j2ee:jndiName=test/txtimer/TimerTest,service=EJB
java.lang.OutOfMemoryError
...
2006-03-20 13:20:25,895 INFO [org.jboss.ejb.plugins.StatelessSessionInstancePool] Registration is not done -> stop
2006-03-20 13:20:25,896 DEBUG [org.jboss.ejb.StatelessSessionContainer] Failed to register pool as mbean
javax.management.InstanceAlreadyExistsException: jboss.j2ee:jndiName=test/txtimer/TimerTest,plugin=pool,service=EJB already registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:757)
at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:225)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)

We need to find out why there OOMEs.