Hmmm... personally speaking I think this article is slightly slanted to ejb3.0
Spring gives a lot of flexibility in its approach and imho will end up complementing ejb3.0 when its finally becomes final.
Its easy to criticise any niggles with spring you may have... but look at the stuff its helped sort out in the time its been around. Spring is constantly maturing as a framework and imho doesn't try to replace, but complement.
I'm not saying ejb3.0 won't be great.... but it may not just be the silver bullet that I think is being hinted at here. :-)