It depends how it's being used, if you use very few apps and/or always clear out recent apps from the multitasker you're less likely to run into iOS needing more memory and triggering a Jetjam event. If you never clear apps from the multitasker they'll remain in RAM until the current active app requires more, combine this with using a bunch of RAM hungry apps like games and you'll stack up Jetjam events. Memory leaks and OS hogging will of course add to this.
This page has information on iOS/OSX memory management including Jetsam. This bit in particular is relevant.
"In iOS, memorystatus/jetsam does not print out messages, but certainly leaves a trail of its victims' carcasses in /Library/Logs/CrashReporter/LowMemory-YYYY-MM-DD-hhmmss.plist - These logs are generated by the CrashReporter, and similar to crash logs they contain a dump. If you have a Jailbroken device, an easy way to force mass executions by jetsam is to run a small binary which keeps on allocating and memset()ing memory in chunks of 8MB (left as an exercise for the avid reader), and run it. You will see applications die, until the offending binary is (eventually) slain."
Very good article! I got most of it, although truth be told I'm not a software guy (I deal with the hardware), but still I got the premise. I do tend to close out my apps often (at least every 3 hours or so) on my iPhone because of the RAM problems. I just got used to doing it after iOS 8 came out. Sometimes it just low resource apps like Messages, but other time its full of apps like Safari and Maps. The memory purging (or Jetsam, which I found out thanks to that article is a past-tense verb and not a noun) has gotten better as I think Apple has compressed iOS more in the most recent releases (like 8.3). It still can cause Safari webpages to reload even if I just deviate for a quick minute, but it's not happening as often which I hope is a sign on things to come with 9.