I'd second that. I've worked on three projects using WebSphere and its always a far harder environment to work with than Weblogic, and double that on Weblogic. I've always found that (unless you use the complete suite of Websphere tools - WSAD and the likes) you need a far better understanding of the
J2EE spec. to try to decode what might be going wrong with your app. I particularaly dislike Websphere's logging architecture - which always felt clunky. Also the command line tool WSAdmin is quite powerful but takes a good while to get used to - and since IBM
still have not completely replicated all its functionality in the Admin Console you still need to rely on it now and then. I've also always though BEA do a very good job on their documentation.
Of course that's purely from a developer's point of view, which is almost never the reason why one is picked over the other.