This truly is one of the fundamental design problems with Entity beans in general. In our application we have some tables that have records in the excess of a million records, so doing a select of every record would be JVM suicide. I find using SessionBeans and DAO's more than suitable, however that is just personal opinion. You can try narrowing ...