PathAddress leaked on reload

Boot server, connect CLI and reload.
On a complex standalone.xml configuration, I can see 150+ PathAddress being leaked.

As an example, the PathAddress [("core-service" => "management"),("management-interface" => "http-interface")] is leaked after the first reload (and only the first one, additional reloads don't create leak).

Attached heapdump, server.log and configuration used (reduced standalone.xml).

server.log contains traces of Instrumented PathAddress. Each created instance has an ID to track finalization.
server.log contains stacktrace of PathAddress allocation.
You will notice:
0) Server starts and allocates 9 PathAddress for the management-interface=http-interface.
1) GC occurs (forced from remote), 7 PathAddress are finalized. Instance 149 and 338 are not finalized.
2) Reload occurs and allocates 9 new PathAddress for the management-interface=http-interface.
3) GC occurs (forced from remote), 8 PathAddress are finalized. Instance 338 is Finalized but NOT instance 149.
4) We have 3 remaining PathAddress 149, 600 and 789
5) Reload occurs and allocates 9 new PathAddress for the management-interface=http-interface.
6) GC occurs (forced from remote), 9 PathAddress are finalized, we still have 149, new ones being 1029 and 1218.

So we have a leak of 1 PathAddress instance, instance 149.