EntityGraph does not load subgraphs correctly

During upgrade from Hibernate 4 to 5 I found out weird loading bug by entity graph.
Structure is simple. I have Activity which have one ActivityPerson as manager and collection of same entities (ActivityPerson) as participants. ActivityPerson has only one field Person. All associations are lazy fetch.

Now if I want load only manager

EntityGraph graph = em.createEntityGraph(Activity.class);
graph.addSubgraph("manager").addSubgraph("person");

or only participants

EntityGraph graph = em.createEntityGraph(Activity.class);
graph.addSubgraph("participant").addSubgraph("person");

Then everything works and printing some field from person is no problem.

System.out.println(act1.getManager().toString());
// or
act2.getParticipant().forEach((p) -> System.out.println(p.toString()));

But if I want load manager and participants then problem occurs. In this simplified version manager was loaded but participants were not loaded and throw could not initialize proxy when is object accessed. (in my project opposite behavior occur but this is not important)

EntityGraph graph = em.createEntityGraph(Activity.class);
graph.addSubgraph("manager").addSubgraph("person");
graph.addSubgraph("participant").addSubgraph("person");
// ...
System.out.println(act3.getManager().toString()); // properly loaded
act3.getParticipant().forEach((p) -> System.out.println(p.toString())); // throws error

I am attaching a simplified project where the bug is reproducible:

This indeed looks like a bug in ORM 5. I quickly tested this on ORM 6.2 though and the problem seems gone, so after an upgrade this should just work for you.

Is this planned to be fixed in ORM 5? Or do I need to upgrade to ORM 6.2?

Unless you are a Red Hat customer and create a support ticket for this or provide the fix yourself, the chances that this will be fixed in 5 are very little.