Why is combining JOIN FETCH with pagination on a one-to-many association a well-known trap?

The JOIN multiplies result rows — one row per child — so applying a LIMIT/pagination to the raw SQL result doesn't correctly limit the number of DISTINCT parent entities; it can cut off partway through a parent's children or produce an incorrect page size, since the database has no concept that multiple rows belong to the same logical parent.