Avoid memory leak from critterism in android

We use criterism in our crash reporting application. We recently started using LeakCanary and the app detects leaks that seem to be caused by critterism. Does anyone know how to set up or manipulate the android SDK for critism to avoid this leak?

* com.my.app.activity.MyActivity has leaked:
* GC ROOT com.my.app.AppInstance.mActivityLifecycleCallbacks
* references java.util.ArrayList.array
* references array java.lang.Object[].[1]
* references crittercism.android.av.g
* references crittercism.android.bd.mPendingResult
* references android.app.LoadedApk$ReceiverDispatcher$Args.this$0
* references android.app.LoadedApk$ReceiverDispatcher.mContext
* leaks com.my.app.activity.MyActivity instance

* Device: motorola motorola XT1254 quark_verizon
* Android Version: 4.4.4 API: 19 LeakCanary: 1.3.1
* Durations: watch=6008ms, gc=210ms, heap dump=3730ms, analysis=29858ms