As we have posted on the Shaderlight forum, this is behaviour that is being caused by Shaderlight. This was discovered following your initial query to Shaderlight support.
This is something that we have now entered in to our system and will hopefully be resolved in a future update of Shaderlight.
Any queries or questions about Shaderlight, please do not hesitate to contact us directly at support@artvps.com or on our forum at http://www.artvps.com/index.php/discuss
Martin