With the @LocalBean support going in, we should maybe consider yanking @Local interfaces from all the examples across the board as really having to have an explicit business local interface is just EJB 3.0 noise.
Logically speaking the @LocalBean view will have all the interfaces the bean implements, so there's rarely a time to use just @Local. We could instead just make a "local-interfaces" example or something and document it as "when you don't want to expose the bean class do it like this...." And document that perhaps @Local is preferred if memory is a concern as each reference to an @LocalBean essentially involves a "do nothing" subclass that takes up a small chunk for each field even though those fields aren't getting used. On that memory note, perhaps for Stateless and Singletons we can just continuously give out the same local bean proxy instance. Cut down on wasted memory just a bit. -David
