It does seem odd. I found this thread, also thinking I'd seen one in the past, but couldn't find it in Javadoc.
I can see the Java developers' point about using specialised classes, and that the presence of a generic Pair class could cause developers to be lazy (perish the thought!)
However, in my experience, there are undoubtedly times when the thing you're modelling really is just a pair of things and coming up with a meaningful name for the relationship between the two halves of the pair, is actually more painful than just getting on with it. So instead, we're left to create a 'bespoke' class of practically boiler-plate code - probably called 'Pair'.
This could be a slippery slope, but a Pair and a Triplet class would cover a very large proportion of the use-cases.