The use case is quite simple:

• child site definition extends a parent, and overrides parts of areas, i.e. availableComponents
• child page template definition extends a parent, and overrides parts of areas, i.e. availableComponents
• these child definitions get merged and you end up with both lists of components to choose from, however one would expect to end up just with those defined on the page template definition level like usually