EJB supports the same stateless approach, but EJB also supports stateful operations. It all comes down to your approach to application development. Roger is a believer in a database-oriented approach to application development. All persistent state should be maintained in a database. The database provides numerous invaluable services such as data integrity, transaction integrity, concurrency control, and access control.
Applications manipulate data in the database.
Any data that have been extracted from the database are potentially invalid because some other application might have changed them since they were retrieved. If you like to develop applications this way, then you would probably be happiest using stateless session beans. But as I said before, one size doesn't fit all. If your database design is relatively simple, and your applications tend to manipulate only one or two tables at a time, then the database-oriented approach is the right one for you. But in my experience, database designs are pretty complicated, and most applications need to manipulate multiple tables at once.