Actually, Spring seems to be hotter. Most of the remotable features of EJB haven't panned out. The Internet has proven to be so hostile that about the only place where you won't bump off a firewall is if you're running a large distributed app completely within the local site and whatever VPN environment it may have. EJB Session beans have been supplanted by Web Services on the open Internet.
What I would concentrate on is JPA. While JPA is part of the EJB3 persistent object spec, it's also usable with Hibernate 3.0 and other ORM technologies as well. You don't need a container like EJB1 and EJB2 did.
Customer surveys are for companies who didn't pay proper attention to begin with.