Let's say we have two classes Customer and Order that have a connection between them. One Customer may have zero, one or many Orders associated.

If I create a Criteria query to read the Orders of a specific Customer I would pass the Customer object as a parameter to the query. In the resulting set of Orders it seems that they are connected to another Customer object with the same data (i e a different object identity). This is not the behaviour I want in my app. What do I need to do to make it return the same Customer object connected to the Order(s)?

I have not implemented the equals() method of my classes (they are generated from EMF). Is this a factor here?
Is there any way I can configure Hibernate and/or my query to get my desired behaviour?
I am also using Teneo since I am using EMF, but to me this seems to be a Hibernate issue, not a Teneo issue.

Hibernate will always guarantee that objects returned from the same session and having the same primary key will be the same instance (==).

That said, the entities must be returned by the Session and not provided by you. In the example you mentioned you should first load the Customer from Hibernate, then use it as parameter. Usually not a problem, as all entities are usually loaded by Hibernate.. so it's more likely that you should widen the scope of your Sessions.