Well, yes... But why would you want to do that ? Is AWS known for giving false positives, which might provide a reason (but not an excuse) for turning it off.
I'm not trying to defend what they did, just trying to understand why they might have done it.
I think it's a reasonable assumption that the driver realised that the activation related to the temporary 85mph speed limit and therefore it didn't affect him, in so far as he didn't need to slow.
No false positives involved, just a realisation by the driver that he had failed to cancel the activation in time and he didn't want to stop, then do what he should have done; with the delays and possible sanctions that would have involved.
Edit
Just to add, it's a reasonable supposition that the actions involved in asking the fireman to disable the AWS relating to the TSR contributed to the crew missing the vital AWS warning for the junction signal. Strange though, because although it doesn't seem to have been mentioned,surely the train would already have passed a double yellow, so surely the restricted aspect of the missed signal should have been expected.
A classic "Red for Danger" scenario where a series of decisions rather than just one thing leads to an incident.
Further edit. I'm wrong about the above, sorry. It was SN43, the yellow before the junction whose warning wasn't cancelled, not the TSR magnet.
The driver having his head out of the cab may be relevant, ie not hearing the warning horn. However it begs the question why did his route knowledge not make him prepare for the horn.
I can't of course condone his actions, but I guess his reasoning for disabling the AWS was still to avoid having to report the activation to the signaller, but why he then failed to slow for the junction is puzzling.