For native applications, Apple says that images larger than 2048x2048 1024x1024 should be avoided and broken down into smaller ones. The problem here is not the size of the file on disk, but the size in memory: the image must be decoded and turned into a "flat" representation.
So, let's say some math: suppose an image is 5000x5000 pixels in size, with 8-bit RGB. This means that each pixel takes 3 bytes:
5000 * 5000 * 3 = 75,000,000 (approximately 71.5 million)
So, you see that your seemingly small image really very quickly fills the memory. iOS can no longer throw away parts if it's under the pressure of memory, it's the whole image or nothing.
Your only solution is to split the image into smaller parts. iOS can then delete images that are no longer visible from the memory (I doubt such a huge image that all parts are visible all the time).
Darkdust
source share