It could have been handled in the class loader. By the time the spec had gone anywhere Java was already transitioning rapidly to servers. The memory usage argument was always bullshit. The JIT internals could have done some many to one type metadata to share function bodies between concrete instances of a particular generic.

I’m sure a bunch of material would have been written describing how to avoid runtime code duplication by tweaking your class hierarchies.