Yes, it could. As long as there is only a single create() method which takes no argument in the component interface, the session bean can be either stateless or stateful(depend on what the bean provider specifies in the deployment decriptor).
I main purpose of using stateful session bean is to preserve conversation. I can't think of the reason to create a stateful session bean with a single create() method which takes no argument.
Nothing up my sleeve ... and ... presto! A tiny ad: