The EntityHome does not implement a local or remote interface, so you would need to work around that. You can create a local interface, subclass the EntityHome and use it like any other stateful bean. I'm not sure whether it can be used with the framework tags in components.xml (even though the entity-home tag has a class attribute that you could point to your new class).
However, that said, the question of whether you need to is debateable given that :
EntityHome is a helper class for orchestrating data access between JSF and the database.It probably won't contain code you want to re-use from outside of the application remotely, and if you are using SeamTransactionManagement, you get the same transactional functions. This is that whole grey area on when to use POJOs versus EJBs.
Regarding the future, EJB 3.1 removes the need for interfaces, so as soon as everyone is on 3.1, we can convert our POJOs to EJBs and vice versa simply by adding and removing the @Stateless annotation.