Actually they are entirely different. We use statefulle session ejb's when we want to store any kind of sate temperorly. This will have scope same to the scope of the object of that bean. But HTTPSession is having scope only on each session id made by the client. Moreover data carrying capability is limited. If you store too much data on Httpsesion, your application definitly will become slow.
As i see it they are both different things. You use httpSessions to store temporary data between page calls and you use an stateful ejb bean to use ejb beans that need some kind of state.
I would not join them both together by inserting the remote interface into the http session. You are bound to have a lot of problems with clustering and you would be limited to in memory session representation. If you need to store something for the session duration i would go for entity ejb and would only store the reference to the ejb pkid into the session.
Sergio Berna<br />Open-VA, a fully accessible open source Validation Authority <br /><a href="http://www.open-va.org" target="_blank" rel="nofollow">www.open-va.org</a>