For some reason, the SPI entries in the hazelcast jar are getting loaded...

... and registered before I have created am instance.  So when I do create a HazelcastInstant, I get exceptions about them already being registered.  I don't think I see any benefit to throwing an exception if they are already registered (ignoring it should be fine right?).  Currently, I commented out the exception throws lines so I can get past the issue, but I'm hoping that maybe a warning could be logged instead since I think logging and ignoring the situation would cause no harm.