SNI is backwards compatible with sites that are not using it, so this is really an asymmetric problem.

If you are writing your REST service with a library that doesn't support SNI then you just fall back to the old one SSL certificate per IP:port. When a browser comes in presenting the SNI option it just gets ignored and life goes on.