Eager load produces unnessessary SQL statement

I have a relationship table that has a Parent and a Child reference to another table. When both of these references are being eager loaded at the same time an unnessessary SQL statement is produced:

SELECT
  [CategoryRelationship].[Id] AS [CategoryRelationship.Id],
  [CategoryRelationship].[ChildCategoryId] AS [CategoryRelationship.ChildCategoryId],
  [CategoryRelationship].[CreatedOn] AS [CategoryRelationship.CreatedOn],
  [CategoryRelationship].[ParentCategoryId] AS [CategoryRelationship.ParentCategoryId],
  [CategoryRelationship].[UpdatedOn] AS [CategoryRelationship.UpdatedOn]
FROM
  [CategoryRelationship];

SELECT
  [Category].[Id],
  [Category].[CreatedOn],
  [Category].[GeographicalAreaId],
  [Category].[IsVisible],
  [Category].[Name],
  [Category].[PropertySetId],
  [Category].[ThingTypeId],
  [Category].[UpdatedOn],
  [Category].[UrlKey]
FROM
  [Category];

SELECT
  [Category].[Id],
  [Category].[CreatedOn],
  [Category].[GeographicalAreaId],
  [Category].[IsVisible],
  [Category].[Name],
  [Category].[PropertySetId],
  [Category].[ThingTypeId],
  [Category].[UpdatedOn],
  [Category].[UrlKey]
FROM
  [Category]

Obviously all results from Category only need to be selected once.

Thanks for drawing this to our attention.  I've logged a bug for it, but we're unlikely to address it immediately, because in the general case both Category queries are required (if there was a Where clause in your query, then the parent and child queries would be different), and it's non-trivial for us to special-case the 'find all' scenario.  If it's causing a significant impact, let us know and we'll review.

Its not important.