The unused methods are still there occupying memory as part of the class / object, even if they're not directly called.
If they were optimised away, then that would make reflective calls on these methods impossible.
One could argue that an optimisation could be generated that only stored the method stub in memory, and garbage collected the method contents (which would then be re-fetched from the class file if a call was made.) However, I'm not aware of a VM which does this, and it would be hard to justify due to the likely minimal gains in memory and tradeoff in speed whenever such a method was called.
Unused inherited methods would be exactly the same.