That is correct. The change was made to be inline with the spec,
otherwise I wouldn't have fixed something that breaks backwards compatibility.
OK. Now, let's say I want to receive X messages in a transactional context, I have a session bean for that (see JmsReceiver on the Wiki).
Should I stop the connection at the end as well?
stop() is invoked when it is returned to the pool, i.e. your connection.close()
It behaves exactly like on a client, except you can't add a message listener.