Grails isn't entirely anemic like our old Spring/Hibernate solution was, which is partly why I like Grails better. The DAO layer and validation is included in the domain class, so you get things like book.save() and book.delete() built into the object, saving precious time coding useless DAO classes. Plus, you can add other cool methods at runtime to the classes too with plugins, giving you all sort of customization ability. But that doesn't help you with PHP.
I still don't agree that business logic, like processing orders would belong in an Order class, but hey that's my current view of things. Years from now I'll look back and think how did I ever get by coding the way I am now.
That stuff aside, I'm interested in which framework you guys decide to go with since one of these days I may get back to programming PHP, although I think it's more likely I'll end up doing Ruby since it seems more and more cheap hosts are adding that to their base features.