It's the same for persistent objects that are never committed and are not related to any object that is still reachable.
This is not related to your question but may still be interesting: When a persistent object IS related to something else and that related object is committed but the initial object isn't, then this object is committed as well automatically when necessary to keep the database in a valid state, but these objects will get an auto-committed status. They are removed from the database when the user that created them logs out or when the server shuts down. The cases when this happens are always either a modelling error or a case where a user closes his browser or navigates away in the middle of a process.