It was my immediate thought as well, but ... Maybe it's a bug in Apache? Ie why it even puts a known invalid OCSP response into TLS hello? Also, note that it's not the only combination that broke. There is a report in the original discussion that the issue rendered a JDK server/client combination unusable as well:
That's why I thought that it needs a deeper inspection probably, digging into standards etc.