Construct 3 uses a different spritesheeting algorithm that is better at combining multiple objects on to the same spritesheet. However if you do things like create lots of objects dynamically at runtime without them being placed on the layout, this can cause higher memory usage as Construct doesn't know ahead of time how to group objects on spritesheets according to when they're used together. See memory usage in the manual for more information on best practices.
If that doesn't help solve it, you can try reducing the spritesheet size in project properties. It can help increase the granularity of image loading, which can bring down the overall memory use.
I found a related post where it talks about layers and transparencies which freed up a lot of space and memory but alas I still have crashing when testing on an ipad air 2.
It is far from a labor intensive game but it does jump back and forth between layers often and I think the memory is hitting a max and crashing, maybe? Everything on screen in the layout is there at the start.
Testing Process - (RAM estimates based of my memory but can get more exact numbers if needed)
Start Game - Logo Layout(this displays my company logo)(50 MB Ram)
Takes you to Main Menu((97 MB RAM)
Click on "Story Mode" Button which takes you to Intro_1 Layout to do a small cutscene(97 MB RAM - this is skipable but for testing sake I run through the whole intro)
This progresses to Intro_2(217 MB RAM)
This progresses to Intro_3(150MB RAM)
This takes you to Player_Select(55 MB RAM)
This takes you to name Entry Layout(50 MB RAM)
This Takes you to Wold_Map(100 MB RAM)
This takes you to the game playl oop
Roll dice on Stage 1 layout(98 MB RAM)
Takes you to Enemy Prep layout(56 MB RAM)
Takes you to Trivia Question Layout(150 MB RAM) - answers all correct answers(2-10 questions depending on enemy)
Takes you to Enemy Defeated Layout(58 MB)
Takes you to Stage 1(or whatever level you are on) - REPEAT
So I find I can get to about the 3rd stage layout which can mean the loop went through about 15-20 times or so and the game resets on the ipad. I have done my best to get the RAM numbers down from like 450 for most of the layouts to a good portion being under 100 MB. I am planning on testing on more devices but I guess I do not understand why it keeps crashing and hoping someone can shed some more light.