I used to put <<Stateless>>, <<Stateful>> to the session beans or <<Entity Bean>>, I usually don't specify if its a EJB 3.0 or 2.1 that will clutter the diagram and will not add any new information about it.
I don't put the Home, Remote and creation objects (like InitialContext) in the diagrams, if you do that your diagram will be 30% bigger and will confuse your developers, they know how to create that kind of components unless you are creating a framework components like a ServiceLocator Cache which will have a special implementation.
if you want to go to a higher level of detail then you will put that, for example if your developers are not well experienced with the EJB behavior.
Now, I did not get a full score on my class diagram, I scored 37 or 38 out of 44. It might be that this is partially due to the stereotype-usage - I don't know. But in RL, I find that most developers find using design patterns as stereotypes to be very helpful. [ January 22, 2008: Message edited by: �dne Brunborg ]