I asked a question on Stack Overflow about a LazyInitializationException I was getting. There is a minimal test case at this location:

http://stackoverflow.com/questions/11604370

It would appear that this is slightly more than the usual Fetch.EAGER/LAZY developer error and it can be shown that find() is not honouring the Fetch.EAGER annotation. A workaround is to issue a Query that simply asks what one would expect "find()" to do.