Thanks for the report. The issue is in our queue but not sure when we will actually work on it. In the meantime, you should be able to workaround this by specifying a join fetch for the association that you want to be eagerly fetched.