iOS - Document removed from a published set not cleared from cache when app is re-opened from background

My Meteor collection seems to be keeping documents in the cache even after they are unpublished by the server (by changing one of their properties) when the app is re-opened from the background after locking the screen.

1. Open the app
2. Add a new document which becomes published
3. Minimize the app/lock the screen
4. Modify the first document so it becomes unpublished and add a new one that is published
5. Re-open the app

If I follow these steps I end up with both documents being returned by my collection().find call, despite the first document no longer being published by the server.

It looks like this is probably an issue with minimongo-cache not properly clearing out data, but I thought it would be best to post the issue here first.

Also, I haven't been able to reproduce the same issue on Android.