I have found and fixed an issue where the presence of an 'On destroyed' trigger would cause the errors reported. It's unfortunate that an unforeseen issue made it in to a stable release. I guess that will teach me to change code before a stable update :P
What I will do is tomorrow or Friday I will issue a 103.2 update. To avoid having to issue a whole new release, and because I think this is only affecting a minority of users who use the 'On destroyed' trigger, I will make a 'quiet' update - I will simply update the existing r103 page, but I will also set the autoupdater to update all r103 users as well so nobody is left using the old broken release.
Sorry for the trouble but hopefully this will be fully resolved shortly, and I will be more careful about code changes before a stable release next time!