it should work, when you specify the target container using the following xdoclet tag
@jboss.container-configuration name="The container config in server/default/conf/standardjboss.xml"
For your second question. Take a look at the Javadoc of a SessionBean.
public void ejbRemove()
A container invokes this method before it ends the life of the session object. This happens as a result of a client's invoking a remove operation, or when a container decides to terminate the session object after a timeout.
Thanks a lot for your help Michael. It was not clear to me from the java doc that the timeout mechanism was handled by the EJB container by default and that I could modify the max-bean-life...
So if I understand this correctly, I don't need to worry about cleaning up if the client session dies without calling the remove operation. The container is keeping track of the stateful session EJB's activity and will throw the timeout when needed.
You can test it writting something to the console in the ejbRemove-method of your ssb. :)