technical architect and software engineer

There is a TA in team and rest of the team is of SE. The TA was trying to create his own time space and individuality and I was disturbed when it started affecting the team's functioning. I was postponing the dialogue because we were in middle of project and I did not want to disturb the rhythm of the team. Finally there was a code review planned for the day that was before the unplanned leave day of TA and I was enraged that it has not yet begun as there was email from the TA to SE asking for path location of the file even though they sit next to each other. I called the TA and asked him the context of the mail and he showed surprise that why was I so enraged, I asked who owned the review if we kept waiting for the mail reply.
I took him to a room and gave him my piece of mind and I think even he was bottled up so he released his venom too. He has been in team for over a year and has not able to gain respect of the team because the SE's have picked up newer changes and older technologies like J2EE faster than he could adopt. So I was giving him individual role as we had invested him by sending him to onsite training etc., I kept suggesting him that he could take help from any on us that he may have took as disrespect remark as he was TA and rest were SE. He made silly comments in meeting and was not contributing even though I had given him enough opportunity in the beginning to speak up. I would have reprimanded him for diverting team's attention and what I was trying to bring in the team say uniform timing wherein everyone is there so that teammates sont have to depend on each other just to complete their task but he took it as a personal offence to his flexible timing. I asked him why he would take cab that left late in night and he said no one questioned him in his 7 years. I asked him why he did not attend team meetings at 10 in morning and he gave me minute by minute break up and brought in his health reasons too.
Also he was after my planning and his designer role. He has done a bad designing job and still felt that it's okay to delay the project by a week if he gets idea in middle of coding stage. Probably the idea is borrowed from Principal (senior consultant) in the team. And he felt sandwiched between the Principal and me as he thought we had a personal enmity and were causing him suffering using designing and scheduling as alibi. Even pointed out that my written communication was poor as I did not reply to his mail that requested the morning meeting to shift from 10 to 10:05.
He expected other designers to be available at 8:30 in night and he did not mind their waiting them till 12 in afternoon because he was senior.
He kept on challenging me to allow him to be thrown out of the project as his previous attempt to get back to unambiguous and straightforward work environment had failed and he had failed to adjust to a team environment where there are less peers and more juniors.
He was very firm in his belief and could not understand why I kept on insisting on team and its goal and how we can help meet them by participating in them.
As for respect I think in software you get it by deeds than by words because in early stage its a technology intensive industry where in youngsters believe that if you want respect than you have to prove it technically.