It's possible that user behavior is causing the onAdClosed event to fire more frequently than the clickthroughs are loaded. Here is the process for what I believe might be happening:
1) The user taps on an ad.
2) The Mobile Ads SDK says, "Great, they want to check out this ad. I'll open a browser."
3) The browser begins to launch.
4) The user decides, "Actually, never mind," and hits the back button.
5) The browser closes without ever launching a request to the AdMob servers.
6) The Mobile Ads SDK says, "Hey, the user came back from the browser, so I'll fire the onAdClosed event."
7) The user resumes normal use of the app.
The AdMob servers record clickthroughs when browsers load the destination page for the ads. That's how they get their data, so if the browser never makes that request, there's no way for the clickthrough to be recorded. The onAdClosed event, however, fires every time the browser is closed, because that's its purpose.
Hopefully this clears up the process a little, and explains why the onAdClosed event might be showing a slightly higher rate.
-Andrew