I suppose it depends on the motivation behind the question. (Although interviews are challenging enough without having to gauge the interviewer's motivation for questions as well as demonstrating a technical knowledge in the answer)
I mean, in my experience, you don't get an EJB Container without a J2EE Application Server. It makes no sense. So yes, sedj, the difference is stupid. It almost makes me think the interviewer didn't *REALLY* understand the technology, and was trying to look like they could ask clever questions. In which case, telling them the question was pointless and pedantic would have exposed the interviewer's naivety and the whole interview would have taken a downturn. Though working in a company which doesn't understand its own technology could be bad news anyway.
If they were trying to trap the OP with a trick question, well, it depends on your standpoint I suppose. My reply above falls into the trap of 'inventing' an anwser to satisfy the interviewer; there is no explicit 'EJB Server', only a concept which we all take for granted as part of the role of a J2EE Application Server.
Tim
---------------------------
"Your morbid fear of losing,
destroys the lives you're using." - Ozzy