Java objects have functionality beyond dispatch tables. Synchronization is one. You can also have x != y where x and y are different objects with the same value.
I do not know whether the standard currently allows for code that is guaranteed to produce Double's with equal values that are not object.Equal to each other, but I doubt that making that impossible will introduce many problems.
May be true, but it's not guaranteed one way or the other. In the Oracle JVM the smaller integers are cached such that
new Integer(10) == new Integer(10)
but new Integer(1000) != new Integer(1000) Integer a;
Integer b;
a = 10;
b = 10;
a == b; // true
a = 1000;
b = 1000;
a == b; // false