The attached test case project shows a situation where using ScrollableResults does not hydrate a proxy object upon join fetch where-as using the JPA getResultList method does.

Start test-case application using maven:
mvn tomcat7:run

1. http://localhost:8080/proxy-fetch-test-case/good
   Association loaded successfully using getResultList()
2. http://localhost:8080/proxy-fetch-test-case/bad
   Association not loaded with lazily loaded exception using ScrollableResults

The expectation was that objects would be loaded identically regardless of using scrollable results or using get result list from JPA.