There are several points to be made regarding your question. I will try my best to address them below.
I know it may sound like nitpicking, but I think it is important to make clear that there is no such thing as "highly homologous". If two proteins share a common evolutionary origin, they are homologous; if they do not, they are not homologous. Homology is binary - two proteins either are or are not homologous. What you can talk about is whether two homologous proteins are highly similar (i.e. have high sequence similarity) or not, but in that case it is entirely your choice how similar two proteins must be to be "highly similar".
Like Stefano said, because homology (and paralogy) is defined by evolution, you normally would have to create evolutionary trees to be able to say anything for sure. However, the reason why one has to do so is to be able to distinguish between orthologs and paralogs (both of which are homologs). However, you are trying to find paralogs within a single organism. Because all your proteins are from the same organism, they by definition cannot be orthologs. In other words, within an organism all homologs are by definition paralogs. I would thus argue that in your specific case there is no need to make phylogenetic trees.
Your question can thus be rephrased to "How high a BLAST score must I have in my database search to infer that two proteins are homologous?". This is a purely statistical question, which E-values were specifically designed to answer. So my advice would be to simply pick an E-value cutoff on the BLAST search in this case. Which one to pick is a tradeoff between sensitivity and specificity - I would normally use something in the range from 1e-3 to 1e-6.
An alternative to this is to not do it yourself. You mention that you work on a model organism, which means that the genome is presumably included in the various orthology databases. You should thus consider extracting paralogs from, for example, the COG/KOG or eggNOG databases.
Take a look at this question. Most of it is applicable to yours as well.
+1 @Michael Schubert