If one were reading HFEJB, one would never have this doubt uncleared.
I can say that stub and skeleton are
deployment-time generated classes which work as
dynamic proxies to the bean. Truely speaking, an EJBObject is a stub and is a dynamic proxy (
Bodyguard in HFEJB literature) to the enterprise bean class. This indirection is the heart and soul of
EJB (and many other latest distributed technologies). While the stub is the
client-side care-taker, the skeleton is the
server-side care-taker (marshalling and unmarshalling of the object copies and IIOP-compltable method arguments for remote objects).
HFEJB speaks only about stubs and not skeletons. You can read RMI for a better understanding.