This pull request si too short.
Have you tested it? Are services still monitored? Why was this call needed before Grails 3 and why it is not needed anymore?
Why writing grailsVersion=3.2.11 in gradle.properties fixes the issue without this PR?
See also apache/grails-core#10715 (comment)

Applying this fix makes one of my test work (that was not working without the change) that modifies the metaclass of a domain class and uses @ConfineMetaClassChanges annotation.

I'll create a project that reproduces this.

I will now check that the plugin still monitor service with that change.

I still get stats about services in my project.

@evernat I've checked that we have this ExpandoMetaClass.enableGlobally() since the SVN version of the plugin, so it's probably linked with an old version of Groovy... Since Martin tested it I think we can merge it.

We can safely remove the call as it's for older Groovy versions (see response of Burt) : https://stackoverflow.com/questions/34447528/what-are-the-costs-of-using-expandometaclass-enableglobally-groovy

Since the services are still monitored and give stats, it's ok to me.